
CONTACT CENTER 7.0 OUTBOUND WEBSERVICES SOFTWARE DEVELOPMENT KIT README

The Contact Center Multimedia (CCMM) Outbound Webservices are installed by default 
when CCMM is installed on a server as part of AACC 7.0 or AACS 7.0 installation.

These Webservices offer a range of SOAP functionality from the default location - either 

  * http://ccmm_server_name/ccmmoutboundwebservices running on port 80

    or

  * https://ccmm_server_name/ccmmoutboundwebservices running on port 443

depending on the active Contact Center security configuration.

The CCMM Outbound Webservices Software Development Kit (SDK) consists of the following elements:

1. The CCMM Outbound Webservices helpfile
2. Sample Outbound Webservices client that demonstrates working with outbound
   campaigns via the soap services functionality.


New in Contact Center 7.0: ACCS Support for Outbound Web Services
=================================================================

Previous releases (6.x) of ACCS did not support Outbound Web Services.
As of Contact Center 7.0 the Outbound Web Services Support is now part of ACCS.
   
+---------------+-------------------------------+   
| Release       | Outbound Web Services Support |
+---------------+-------------------------------+   
| ACCS 6.x      | No                            |
+---------------+-------------------------------+
| ACCS 7.x      | Yes                           |
+---------------+-------------------------------+

   

Sample Outbound Webservices client
==================================

This utility allows users to log into CCMM using administrative user credentials
to work with campaigns (campaign and campaign member search and modification are
implemented). It illustrates the basic pattern of validating and connecting to
Outbound Webservices, as well as manipulating campaigns using Outbound
Webservices functionality.

Note: An administrator user must be created in advance using CCMM Admin client.

The solution can be opened via the .sln file "Outbound WebservicesClient.sln". 
It was created in Visual Studio 2010. It has been validated to work with Visual
Studio 2013. (Opening the solution in Visual Studio 2013 will prompt for "one-way
upgrade" and this has been validated to work successfully.)

Before execution, the "Service References" shown in the Solution Explorer should
be updated to point to the appropriate web services on a deployed CCMM 7.0 installation. 

To do this, 

 - Select each of the Service References in turn 
 - Rightclick on the service reference and select the Configure service reference option 
 - Input your CCMM server IP address, being careful to specify the correct
   protocol (http, or https) for the active security mode on the AACC server. 

If you are still having difficulty or you have moved back to Visual Studio 2008
and are having problems with the "Service References" you may delete the 
service reference and recreate it, pointing to your own server, but using the 
current naming conventions, i.e., 

 - http(s)://CCMM_IP_ADDRESS/ccmmoutboundwebservices/OutboundUtilityWS.asmx 

If you are working with an AACC server that is running in Secure mode (HTTPS
only, which is the default for Contact Center 7.0), and the target CCMM server 
is operating on the install-provided security certificate you will need to 
disable certificate validation in the app.config settings file of the sample
client,

  <configuration>
    <system.net>
      <settings>
        <servicePointManager checkCertificateName="false"/>
      </settings>  
    </system.net>
  </configuration>
     
(Also note that Visual Studio may prompt you with a security warning due to the use of this certificate.)

The client is now ready to build and execute against your Contact Center 7.0
CCMM installation.


Note:
-----
Contact Center 7.0 uses Microsoft .Net version 4.5.2. The sample application has
been tested with .Net 4.5.2 and Visual Studio 2013.


USING THE SAMPLE CLIENT:
------------------------
Login to CCMM using the pre-configured administrator ID/password. This calls a 
login web service which returns a session key; the session key is used for validation 
throughout all subsequent web service calls.

Once connected, the Client loads active campaigns. When a campaign is selected
in the left pane of the user interface the contacts of that campaign are listed.
The buttons can be used to query, modify, and delete existing contacts, as well
as create new contacts.

The Outbound Webservices does not provide functionality for creating a campaign.
To fully exercise the capabilities of the Outbound Webservices one or more campaigns 
need be created in advance using the CCMM OCMT tool.

To add a contact not all fields provided are mandatory, i.e., although name,
international access code etc can be specified, just phone number is sufficient 
to successfully add a contact to a campaign using this demonstration application.
